Optimization of the presence information refresh for a wireless device

ABSTRACT

In various embodiments, a mobile device and/or the presence-aware applications running on the device may be configured to support multiple user profiles. For instance, multiple users with access to the same mobile device may each create a user profile and login credentials on that device, and each user may take turns using the mobile device. The mobile device may also allow multiple users to access the mobile device simultaneously. In such embodiments, the mobile device processor executing the presence module and/or presence engine may be configured to associate a particular user profile with a request for updated presence information and determine whether to update the presence information based at least in part on the that user profile.

RELATED APPLICATIONS

This application is a continuation-in-part of U.S. patent application Ser. No. 13/963,145 entitled “Optimization of the Presence Information Refresh for a Wireless Device” filed Aug. 9, 2013, which is a continuation of U.S. patent application Ser. No. 12/781,461, entitled “Optimization of the Presence Information Refresh for a Wireless Device” filed May 17, 2010, now U.S. Pat. No. 8,520,613, the entire contents of all of which are hereby incorporated by reference.

BACKGROUND

The present invention generally relates to wireless telecommunication systems. More particularly, the present invention relates to techniques for optimizing presence information refresh rates for wireless devices that utilize a wireless telecommunication network.

Presence information is one of the most important enabling data for mobile device multimedia services. In order to enable mobile instant messaging, group chat, media sharing, and other forms of communication, the mobile device user needs to have the presence information of his or her contacts and know the capabilities of his or her contact's mobile devices. There exist several different standardized methods for providing up-to-date presence information to a mobile device. However, the cost of updating presence information over commercial wireless network is quite significant in terms of over-the-air resources needed for request and transmission of this data. The overhead needed in the wireless telecommunication network is thus much higher than using a fixed network.

Given the high overhead requirements for presence information on a wireless communication network, techniques for optimizing the timing and conditions associated with a presence information update request are desirable. It is thus to such techniques that the present disclosure is primarily directed.

SUMMARY OF THE INVENTION

An embodiment of the present disclosure includes a system, and in the exemplary embodiment, the system includes, but is not limited to, a mobile device configured to cache presence information; wherein the mobile device is configured to store state information for a plurality of available communications channels, wherein each communication channel is associated with a different communication protocol; wherein the mobile device is configured to store presence information accessible to a plurality of applications installed on the mobile device; wherein the mobile device is configured to select an available communication channel from the plurality to send a request for updated presence information; wherein the mobile device is configured to update the presence information via the selected communication channel with information received from a remote computer system in response to a comparison of a quantification to a threshold; and wherein the mobile device is configured to calculate the quantification from at least load information for a base transceiver station. In addition to the foregoing, other system techniques are described in the detailed description, the drawings, and the appended claims.

An embodiment of the present disclosure includes a system, and in the exemplary embodiment, the system includes, but is not limited to, circuitry for comparing a quantification calculated from at least information that indicates a load on a base transceiver station; and circuitry for sending a request for updated presence information to the base transceiver station of an access network in response to the comparison. In addition to the foregoing, other system techniques are described in the detailed description, the drawings, and the appended claims.

An embodiment of the present disclosure includes a computer readable storage medium, in the exemplary embodiment, the computer readable storage medium includes, but is not limited to, instructions for detecting a plurality of available communication channels, wherein each available communication channel is associated with a different communication protocol; instructions for selecting an available communication channel from the plurality; and instructions for sending a request for updated presence information via the selected available communication channel. In addition to the foregoing, other computer readable storage medium techniques are described in the detailed description, the drawings, and the appended claims.

An embodiment of the present disclosure includes a method, and in the exemplary embodiment, the method includes, but is not limited to storing a plurality of applications configured to request presence information from an operating system of a mobile device; receiving, by a mobile device operating system, a request for presence information from an application of the plurality of applications; comparing a timestamp associated with cached presence information to a threshold; and updating the presence information in response to the comparison. In addition to the foregoing, other method techniques are described in the detailed description, the drawings, and the appended claims.

An embodiment of the present disclosure includes a method, and in the exemplary embodiment, the method includes, but is not limited to, storing a plurality of applications configured to request presence information from an operating system of a mobile device; receiving, by a mobile device operating system, a request for presence information from an application of the plurality of applications; comparing a timestamp associated with cached presence information to a threshold; and sending the cached presence information to the application in response to the comparison. In addition to the foregoing, other method techniques are described in the detailed description, the drawings, and the appended claims.

An embodiment of the present disclosure includes a device, and in the exemplary embodiment, the device includes, but is not limited to, means for receiving a request for presence information from an application executing on the mobile device; means for determining that a transceiver of the mobile device is transmitting data on a reverse channel to a base transceiver station; and means for sending a request for updated presence information over the reverse channel. In addition to the foregoing, other device techniques are described in the detailed description, the drawings, and the appended claims.

An embodiment of the present disclosure includes an access terminal, and in the exemplary embodiment, the access terminal includes, but is not limited to, circuitry for caching a presence information update request; circuitry for comparing a quantification for the presence information update request to a threshold, wherein the threshold is calculated from at least information that indicates a load on a base transceiver station; and circuitry for sending the presence information update request to the base transceiver station in response to the comparison. In addition to the foregoing, other access terminal techniques are described in the detailed description, the drawings, and the appended claims.

An embodiment of the present disclosure includes an access terminal, and in the exemplary embodiment, the access terminal includes, but is not limited to, circuitry for caching a presence information update request; circuitry for comparing a length of time that the presence information update request has been cached to a threshold; and circuitry for sending the presence information update request to the base transceiver station in response to the comparison. In addition to the foregoing, other access terminal techniques are described in the detailed description, the drawings, and the appended claims.

An embodiment of the present disclosure includes an access terminal, and in the exemplary embodiment, the method includes, but is not limited to, circuitry for executing a push to talk application, wherein the push to talk application includes a list of contacts; circuitry for caching presence information for the list of contacts; circuitry for comparing a length of time that the presence information for the list of contacts has been cached to a threshold; and circuitry for sending a request to update the presence information for the list of contacts in response to the comparison. In addition to the foregoing, other access terminal techniques are described in the detailed description, the drawings, and the appended claims.

In further embodiments, a mobile device and/or the presence-aware applications running on the device may be configured to support multiple user profiles. For instance, multiple users with access to the same mobile device may each create a user profile and login credentials on that device, and each user may take turns using the mobile device (e.g., one user may log in/access the mobile device after another user has finished/logged out of the device). In another embodiment, the mobile device may allow multiple users to access the mobile device simultaneously (e.g., a gaming device that supports multiple players). In such embodiments, the mobile device processor executing the presence module and/or presence engine may be configured to associate a particular user profile with a request for updated presence information and determine whether to update the presence information based at least in part on the that user profile.

The foregoing is a summary and thus contains, by necessity, simplifications, generalizations and omissions of detail. Those skilled in the art will appreciate that the summary is illustrative only and is not intended to be in any way limiting.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 describes an exemplary computer system.

FIG. 2 depicts an exemplary mobile communication device.

FIG. 3 shows an exemplary wireless network.

FIG. 4 depicts an exemplary mobile device.

FIG. 5 depicts an operational procedure for practicing aspects of the present disclosure.

FIG. 6 depicts an operational procedure for practicing aspects of the present disclosure.

FIG. 7 depicts an operational procedure for practicing aspects of the present disclosure.

FIG. 8 depicts an operational procedure for practicing aspects of the present disclosure.

FIG. 9 is a component block diagram of another mobile device suitable for use in an embodiment.

FIG. 10 is a process flow diagram of an embodiment method for updating presence information based on user profiles.

DETAILED DESCRIPTION

In this disclosure, the terms ‘communication device,’ ‘wireless telephone,’ ‘wireless communications device,’ ‘handheld device,’ ‘wireless communication device,’ ‘handset,’ ‘access terminal,’ ‘mobile device,’ and ‘mobile station’ are used interchangeably. The terms ‘call’ and ‘communication’ are also used interchangeably. The term ‘exemplary’ means that the disclosed element or embodiment is only an example, and does not indicate any preference of use. Further, like numerals refer to like elements throughout the several drawings, and the articles “a” and “the” include plural references, unless otherwise specified in the description. It can be appreciated by one of skill in the art that one or more various aspects of the disclosure may include but are not limited to circuitry and/or programming for effecting the herein-referenced aspects of the present disclosure; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced aspects depending upon the design choices of the system designer.

The term circuitry used throughout the disclosure can include hardware components such as application specific integrated circuits, hardware interrupt controllers, hard drives, network adaptors, graphics processors, hardware based video/audio codecs, and the firmware/software used to operate such hardware. The term circuitry can also include microprocessors configured to perform function(s) by firmware or by switches set in a certain way or one or more logical processors, e.g., one or more cores of a multi-core general processing unit. Logical processor(s) can be configured by software instructions embodying logic operable to perform function(s) that are loaded from memory, e.g., RAM, ROM, firmware, etc. In exemplary embodiments, where circuitry includes a combination of hardware and software, an implementer may write source code embodying logic that is subsequently compiled into machine-readable code that can be executed by a logical processor. Since one skilled in the art can appreciate that the state of the art has evolved to a point where there is little difference between hardware, software, or a combination of hardware/software, the selection of hardware versus software to effectuate functions is merely a design choice. Thus, since one of skill in the art can appreciate that a software process can be transformed into an equivalent hardware structure, and a hardware structure can itself be transformed into an equivalent software process, the selection of a hardware implementation versus a software implementation is left to an implementer.

Embodiments may execute on or use data stored on one or more computers. FIG. 1 and the following discussion are intended to provide a brief general description of a suitable computing environment in which the disclosure may be implemented. One skilled in the art can appreciate that computer systems disclosed herein can have some or all of the components described with respect to computer 100 of FIG. 1.

Referring now to FIG. 1, an exemplary computer system 100 is depicted. Computer system 100 can include a logical processor 102, e.g., an execution core. While one logical processor 102 is illustrated, in other embodiments computer system 100 may have multiple logical processors, e.g., multiple execution cores per processor substrate and/or multiple processor substrates that could each have multiple execution cores. As shown by the figure, various computer readable storage media 110 can be interconnected by a system bus that couples various system components to the logical processor 102. The system bus may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. In exemplary embodiments the computer readable storage media 110 can include for example, random access memory (RAM) 104, storage device 106, e.g., a electromechanical hard drive, a solid state hard drive, etc., firmware 108, e.g., FLASH RAM or ROM, and removable storage 118 such as, for example, CD-ROMs, floppy disks, DVDs, FLASH drives, external storage devices, etc. It should be appreciated by those skilled in the art that other types of computer readable storage media can be used to store data, such as magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, etc.

The computer readable storage media 110 provides storage of computer readable instructions, data structures, program modules and other data for the computer 100. A basic input/output system (BIOS) 120, containing the basic routines that help to transfer information between elements within the computer system 100, such as during start up, can be stored in firmware 108. A number of applications and an operating system 122 may be stored on firmware 108, storage device 106, RAM 104, and/or removable storage devices 118, and executed by logical processor 102.

Commands and information may be received by computer 100 through input devices 116 which can include, but are not limited to, keyboards and pointing devices. Other input devices may include microphones, joysticks, game pads, scanners or the like. These and other input devices are often connected to the logical processor 102 through a serial port interface that is coupled to the system bus, but may be connected by other interfaces, such as a parallel port, game port or universal serial bus (USB). A display or other type of display device can also be connected to the system bus via an interface, such as a video adapter which can be part of, or connected to, a graphics processor 112. In addition to the display, computers typically include other peripheral output devices (not shown), such as speakers and printers. The exemplary system of FIG. 1 can also include a host adapter, Small Computer System Interface (SCSI) bus, and an external storage device connected to the SCSI bus.

Computer system 100 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer. The remote computer may be another computer, a server, a router, a network PC, a peer device or other common network node, and typically can include many or all of the elements described above relative to computer system 100.

When used in a LAN or WAN networking environment, computer system 100 can be connected to the LAN or WAN through a network interface card 114 (NIC). The NIC 114, which may be internal or external, can be connected to the system bus. In a networked environment, program modules depicted relative to the computer system 100, or portions thereof, may be stored in the remote memory storage device. It will be appreciated that the network connections described here are exemplary and other means of establishing a communications link between the computers may be used. Moreover, while it is envisioned that numerous embodiments of the present disclosure are particularly well-suited for computerized systems, nothing in this document is intended to limit the disclosure to such embodiments.

Referring now to FIG. 2, it illustrates a mobile device 200 including a display 204. The mobile device 200 can include a computer platform 206 that can handle voice and data packets, execute software applications, and transmit information across a wireless network. The computer platform 206 includes, among other components, at least one processor 208 such as an application-specific integrated circuit (“ASIC”) or a RISC processor such as those that implement the ARM architecture. The processor 208 is installed at the time of manufacture of the wireless communication device 200 and is not normally upgradeable. The processor 208 can execute an application programming interface (“API”) layer 210, which can include an operating system that can control the hardware of the mobile device. An example of an operating system is the “binary runtime environment for wireless” (BREW) software developed by QUALCOMM® for wireless communication device platforms.

As shown here, the mobile device 200 can be a wireless communication telephone, but can also be any wireless device with a computer platform 206 as known in the art, such as a personal digital assistant (PDA), a pager with a graphics display, or even a separate computer platform 206 that has a wireless communication portal, and may otherwise have a wired connection to a network or the Internet. Memory, i.e., computer readable storage media, 212 can be comprised of read-only or random-access memory (RAM and ROM), EPROM, EEPROM, flash cards, or any memory common to computer platforms. The computer platform 206 can also include a local database 214 for storage of software applications not actively in memory 212. The local database 214 is typically comprised of one or more flash memory cells, but can be any secondary or tertiary storage device as known in the art, such as magnetic media, EPROM, EEPROM, optical media, tape, or soft or hard disk.

The computer platform 206 can also include a communication interface 216 that can be used to open a data channel to an endpoint such as a media server. The communication interface 216 can also be part of the standard communication interface for the mobile device 200 which ordinarily carries the voice and data transmitted to and from the wireless communication device 200. The communication interface 216 typically is comprised of hardware that is known in the art.

Continuing with the description of FIG. 2, additionally depicted is a diagram of software layers of that can execute on the processor 208. In an embodiment, computer platform 206 can include a series of software “layers” developed on top of the Mobile Station Modem (MSM) 218 and the Advanced Mobile Subscriber Software (AMSS) 220, developed by QUALCOMM®. In this example, the underlying MSM chipset can implement the software protocol stack for the entire suite of CDMA communication technologies that include CDMA2000 1X and CDMA2000 1xEV-DO. In this example, the AMSS 220 can be configured to support a mobile operating system layer 222, which in an embodiment is BREW®. The mobile operating system layer 222 can provide an application programming interface for chip or device-specific operations, while providing an isolation layer that eliminates direct contact to the AMSS 220 and any OEM software on the mobile device 200. The mobile operating system layer 222 can enable application development that uses wireless communication device features without having to rewrite the application each time a new release of the device-specific software is released.

In this example, the mobile operating system 222 is shown including a presence module 250. Presence module 250 is shown in dashed lines which indicates that it is considered optionally located within the operating system, and the disclosure is not limited to the illustrated embodiment.

Continuing with the description of FIG. 2, it also shows that operating system 222 can support the execution of one or more applications 224 such as media clients, e.g., content players, instant messenger programs, push to talk applications, map applications, or any other application that uses presence information.

Turning to FIG. 3, an exemplary wireless network is illustrated. The wireless network is merely exemplary and can include any system whereby remote modules communicate over-the-air between and among each other and/or between and among components of a wireless network, including, without limitation, wireless network carriers and/or servers. As one of skill in the art can appreciate, each element can be effectuated by one or more computer systems including elements such as those described above with respect to FIG. 1. As illustrated by the figure, mobile device 200 (while one mobile device is shown one skilled in the art can appreciate that many more can simultaneously use the wireless network) can be in wireless communication with an access network 304 which can include base transceiver station 326 and base station controller 302. Access network 304 includes the equipment that provides data connectivity between a packet-switched data network and mobile devices over an air interface such as, for example, 1X-EV DO or the High rate packet data (HRPD) air interface.

For example, an HRPD system is like a CDMA system and uses spread spectrum and interference averaging to allow frequency reuse within a cell. In the forward link all physical channels are time multiplexed on a single composite channel whereas in the reverse link physical channels are code multiplexed and grouped as those used in the access mode or traffic channel mode. Reverse traffic channel mode includes a data channel which is used to carry user traffic from the mobile device to the base transceiver station.

Continuing with the description of FIG. 3, an access node authentication, authorization, and accounting server “AAA” 328 used to authenticate mobile devices can be coupled to a database operable to store information such as user accounts and privileges.

Data packets can be routed from the access network 304 to the packet data servicing node 308 (PDSN) via a packet controlled function 306 (PCF). PCF 306 is an element, e.g., one or more computer systems, that controls the transmission of packets between an access network and a PDSN. The PCF can be configured to keep track of registration and sessions, control available radio resources, buffer data received from PDSN until radio resources are available, etc. PDSN 308 includes equipment configured to provide data connectivity between a radio access network and a packet-switched data network 310 such as the Internet. Coupled to the packet-switched data network 310 is/are presence server(s) 330, which are configured to store presence information for a plurality of applications.

Presence information can include status indicators that convey the ability and willingness of a potential communication partner, location information, device capabilities, and the like. Common status indicators that indicate a user's willingness to communicate are “free for chat,” “busy,” “away,” “do not disturb,” and “out to lunch.” Information that conveys the ability of the user to communicate can indicate whether the user is online or offline. In exemplary embodiments, device capabilities could include whether the device includes a push-to-talk application, can handle text messages, can handle streaming media, includes a camera, includes a music player application, or whether the user's service plan enables certain features.

Presence aware applications can obtain presence information from presence servers 330. For example, a presence aware application can be affiliated with one or more servers that store its presence information in a presence record called a “presentity.” The presentity can be made available for distribution to other users to convey his or her presence information to compatible applications. A specific example could include a presence server that stores a user's online/offline status for a push to talk application. The presence server can make this online/offline status information available to other devices that run a compatible push to talk application. In this example, a presence module 250 on a mobile device could receive a request from a push to talk application for status information and the presence module 250 can determine how to optimize use of the access network by, for example, determining whether to use a different access method to obtain presence information, delay the request until network conditions are favorable, and/or respond with cached presence information.

Voice packets can be routed to a mobile switching center 312 (MSC). A MSC is the primary service delivery node responsible for handling voice calls and SMS as well as other services (such as conference calls, FAX and circuit switched data). Connected to a MSC are a home location register 312 (HLR) and the public switched telephone network 314 (PSTN). The HLR is the location register to which a user identity is assigned for record purposes such as subscriber information. The HLR is the first database that is interrogated to obtain mobile location and routing information once a mobile device's number is dialed by a user outside the network.

Turning now to FIG. 4, which shows a mobile device 200 including a presence module 250. As illustrated by the figure, the presence module 250 is shown as a single point of contact on mobile device 200 for presence requests from presence aware applications 402, 404, and 406. For example, an application program interface can be made available to presence aware applications. In an exemplary embodiment, a presence aware application can register with the presence module 250 and indicate to presence module 250 what type of presence information it is interested in, e.g., location information, device state information, or application specific presence information. The presence module 250 can then configure one or more stores, e.g., memory, in a cache of memory 212 to store received presence information. In an exemplary embodiment, the presence module 250 can store information that multiple applications use in a common store and store application specific information in an application specific store. For example, the presence module 250 can cache location information once in a common store and store, for example, status information for buddies in an application specific store.

The presence module 250 can optimize the presence information update requests by reducing the amount of access network resources while taking application performance into account. As shown by the figure presence module 250 can use different communication channels effectuated by different access technologies to obtain presence information from presence servers 330. For example, FIG. 4 shows four different access methods that can be used to access packet-switched data network 310 through a communication port 408 or a wireless transceiver 410. A communication port 408 can be a port that connects the mobile device 200 to a packet-switched data network 310 either directly or via a physical bridge. For example, a communication port 408 can include an Ethernet port that connects the mobile device 200 to a packet-switched data network 310 directly or it can be a USB port that is used to physically connect the mobile device 200 to a router or computer that is directly or indirectly connected to packet-switched data network 310.

As shown by the figure, the wireless transceiver 410 is indicated in dashed lines which indicates that it can be a single component or multiple components that implement multiple wireless technologies. For example, in an embodiment the wireless transceiver 410 can communicate with a device via a communication channel that conforms to the 802.15 communication standard such as a Bluetooth® device. In the same or another embodiment the wireless transceiver 410 can communicate with a device via a communication channel that conforms to the 802.11 communication standard such as a Wi-Fi® device. In the same or another embodiment the wireless transceiver 410 can communicate with access network 304 using a communication channel that conforms to the HRPD standard.

The presence engine 400 can be configured to attempt to update presence information via these other communication channels, or open traffic channels in an exemplary embodiment. Thus, in this exemplary embodiment, additional access network resources would not have to be used to update the presence information. For example, the presence engine 400 can be configured to use an algorithm that uses channel performance information, values assigned by the access technology, and open channels to select a channel to update over.

For example, the mobile device 200 can detect available access technologies and store a list of them in memory. The presence engine 400 can look up the access technologies, obtain preference values for them that can be assigned by an access network admin, and adjust the values based on whether a channel of that type is already open. Or put another way, a preference can be given to channels that are already open and being used to send/receive information. The presence engine 400 can then calculate, or use a lookup table to obtain, data rate information. After data rate information is quantified and associated with values presence engine 400 can then generate scores for each available communication channel and select the “best” one. The presence engine 400 can then send the request using the selected access technology.

In some exemplary embodiments the presence engine 400 can be configured to determine whether to use a channel to update presence information or return cached information instead. For example, the presence engine 400 can be configured to perform this operation after a channel is selected, before a channel is selected, or without selecting a channel (in this last case the presence engine 400 may be configured to only use a reverse traffic channel for updates). The presence engine 400 can determine whether or not to update presence information using an algorithm that uses various information stored in memory 212 as inputs and calculates a quantification. In this exemplary embodiment, the presence engine 400 can then compare the quantification to a threshold and determine whether or not to update the presence information.

In an exemplary embodiment, the presence engine 400 can be configured to determine whether to update presence information from information associated one or more timestamps associated with cached presence information. For example, in an embodiment where timestamps are used, the presence engine 400 can compare the current timestamp to a timestamp associated with the requested type of presence information. The presence engine 400 can then use an algorithm that takes this information into account and generate a quantification. The quantification can then be compared to a threshold to determine whether or not the presence information should be updated.

In the same, or another exemplary embodiment, priority information associated with an application requesting the presence information can be used to generate the quantification. For example, each application can be associated with priority information that indicates the importance of the application. In a specific example, an E-911 application that sends location information to emergency personal can have a higher priority than other applications. In this exemplary embodiment, the presence engine 400 can identify the requesting application and lookup a priority score for the application. The presence engine 400 can then use an algorithm that takes this information into account and generate a quantification. The quantification can then be compared to a threshold to determine whether or not the presence information should be updated.

In the same, or another exemplary embodiment, user profile information can be used to generate the quantification. For example, each mobile device can be associated with a user account that has a score based on the importance of the user. In a specific example, an emergency-personnel user can have a higher priority score than a regular user. In another specific example, a user that pays a fee for premium service can have a higher priority score than a regular user. In this exemplary embodiment, the presence engine 400 can obtain the score associated with the user account and execute an algorithm that takes this information into account and generate a quantification. The quantification can then be compared to a threshold to determine whether or not the presence information should be updated.

In the same, or another exemplary embodiment, how the device is being used can be used to generate the quantification. For example, information that identifies whether a user is actively interacting with the mobile device 200 can be used to affect the quantification. In this example, if the mobile device 200 is being used it may be more likely that the presence information is updated in order to influence the user's experience using the mobile device 200.

In the same, or another exemplary embodiment, current access network conditions can be used to determine the quantification. For example, each access network, e.g., each base transceiver station, can measure current network conditions and send information to the mobile devices it services to indicate, for example, the load on the base transceiver, current interference levels, available bandwidth, etc. For example, the forward link channel can include a medium access control channel that has load information such the number of channels in use, the level of activity in sector, e.g., interference level, etc. This information can be mapped to a table that quantifies the possible values and the information can be used by presence engine 400 to calculate the quantification. The quantification can then be compared to a threshold to determine whether or not the presence information should be updated.

In an alternative embodiment the threshold can be set based on the current access network conditions instead of or in addition to the quantification. Similar to that described above, current network conditions can be measured and sent to the mobile devices it services to indicate, for example, the load on the base transceiver. For example, the presence engine 400 can be configured to receive information that defines the load on the base transceiver station 326. This information can be mapped to a table that quantifies the possible values and the information can be used by the presence engine 400 to calculate the threshold.

Continuing with the description of FIG. 4, in an embodiment of the present disclosure the presence module 250 can be configured to delay, deny or immediately send presence information requests based on information such as, user settings, device settings, access network settings, device state, user profile settings, and the like. For example, a user may set settings that indicate whether or not an application can request presence information. In the same, or another embodiment where a user-initiated update is received, e.g., a user pressed a refresh button, the presence module 250 can send the request without running the presence engine 400. In the same, or another embodiment, a network policy can be received that identifies whether presence information updates should be triaged. For example, a base transceiver station could broadcast information that can be used to configure the presence module 250 to disable the presence engine 400 in a zone that has a light load.

FIGS. 5-8 are a series of flowcharts depicting operational procedures. Those having skill in the art can appreciate that the style of presentation utilized herein, e.g., beginning with a presentation of a flowchart(s) presenting an overall view and thereafter providing additions to and/or further details in subsequent flowcharts, generally allows for a rapid and easy understanding of the various operational procedures. Furthermore, those of skill in the art that certain operations can be executed in a different order than described herein, thus, the disclosure is not limited to any specific order of operations.

Turning now to FIG. 5, an exemplary operational procedure for practicing aspects of the present disclosure is shown. Operation 500 begins the operational procedure when, for example, an application such as a map application accesses an API and requests preference information, e.g., location information for the mobile device 200. For example, the application could request presence information in response to receiving a request from a user, or the application could be configured to periodically request presence information. Alternatively, operation 500 could begin in response to a delay operation. For example, presence module 250 may have received a request, measured access network information, and determined to wait for network conditions to become more favorable before requesting data. Thus, the request could be cached and presence module 250 could run the operational procedure of FIG. 5 after a predetermined amount of time.

Continuing with the description, at decision 502, the presence module 250 can be configured to determine if features of the presence module have been enabled. In one embodiment, if a reverse traffic channel is permitted to send presence information, then the method will proceed to step 504 to update the presence information via reverse traffic channel and then store the updated presence information in memory, as shown at step 514, and then the presence information will be sent to the calling resident application, as shown at step 516.

Alternately, a settings override can be set to send the presence information only on non-access network based channels, and the process will proceed to step 508. Then the non-access network based channel will be selected and the presence information will be updated via that channel, as shown by step 512. The updated presence information will then be stored in memory, as shown at step 514, and then the presence information will be sent to the calling resident application, as shown at step 516.

In another embodiment, if settings do not support the immediate requesting of presence information through the use of a channel, then the presence information can be sent from memory to the requesting resident application, as shown at step 516. Otherwise, if no specific settings override exists at decision 502, then the presence module 250 can detect all available communication channels to send the presence information, as shown at step 506. Other settings for communication channel transmission can likewise be set for the presence module 250 as needed.

To originally obtain any settings information, the presence module 250 can access a data structure in memory that can store information indicative of specific device settings, e.g., network and/or user profile settings. In an embodiment, this information can be used to configure presence information updates. For example, the data structure could store information that configures presence module 250 to enable/disable updates via access network 304. In another example, the data structure could store information that configures presence module 250 to disable access network updates and presence module 250 can be configured to select a non-access network communication channel to update presence information (if one is present), as is shown at step 508. In another exemplary embodiment, the data structure in memory can store network settings or user profile settings which can indicate that the user's account does or does not authorize the user to automatically obtain a data channel to receive presence information updates. In this example, the user would have to instead have his or her request processed by presence engine 400.

As shown by FIG. 3, if overrides authorize direct presence information updates then the presence module 250 can send one or more packets of information indicative of the presence information update on a reverse traffic channel to base station transceiver 326. With reference to FIG. 3, the request can be routed to the PDSN 308 and one or more TCP/IP packets can be routed to the presence server that stores the requested presence information. For example, the request could be for the online/offline status of friends in a contacts list. The updated presence information (online/offline status) can be routed back to mobile device 200 and stored in a presence information cache in memory 212 as shown by operation 514. Operation 516 shows that the presence module 250 can be configured to return presence information stored in cache to the requesting application. In this example, the returned presence information would include the updated online/offline status of friends in contact list.

As illustrated by FIG. 5, if an override configures the presence module 250 to provide cached information then, as illustrated by the path directly to operation 516, the presence module 250 can return presence information stored in memory 212 to the requesting application. Continuing with the example, from above, since the online/offline status of friends was not updated then the information may not reflect the current situation.

As illustrated by operation 506, in an embodiment of the present disclosure the presence engine 400 can detect the available communications channels. For example, the presence engine 400 can survey a site and identify available wireless networks, Bluetooth devices, HRPD channels, etc. Based on the site survey the presence engine 400 can determine (at operation 510) whether or not a new reverse traffic channel will need to be opened with base transceiver station 326 in order to service the request. For example, the site survey may indicate that no other channels are available, or the presence engine 400 may determine that the best communication channel is provided by access network 304. Turning to operation 512, if a new reverse traffic channel is not needed the update request can be sent via a selected communication channel, e.g., if a reverse channel is opened the request can be sent via that channel, or if a 802.11 channel is available it can be sent via that channel, etc.

Turning to operation 518, in an embodiment where a new reverse traffic channel is selected at decision 510, the presence engine 400 can determine whether to return cached information, or use access network 304 to obtain updated presence information. Turning to operation 518, a quantification can be determined from various information, e.g., network conditions, timestamps, etc., and the quantification can be compared to a threshold. Presence engine 400 can either update presence information (operation 504) or returned cached information (operation 516) based on the comparison.

Turning now to FIG. 6 there is shown an operational procedure for practicing aspects of the present disclosure. FIG. 6 illustrates an embodiment in which the presence module 250 is configured to check to see if requested presence information is old before determining whether to update the information. Operation 600 begins when the presence module 250 receives a request from an application for presence information, e.g., location information. The presence module 250 can run and determine what information the application is requesting and the presence information cache for the presence information. In this exemplary embodiment, multiple applications may use the requested presence information and the presence module 250 may have previously obtained the information within a short period of time. Thus, as illustrated by operation 602, the presence module 250 can be configured to check to determine whether it has the desired information before determining whether to update the information.

As shown by operation 604, if the presence module 250 detects the desired presence information it can determine whether the information has been stored in cache for a length of time greater than a predetermined threshold. Predetermined threshold could be a value that is set in accordance with, access network information, a user profile, and/or the priority associated with the requesting application. For example, a user profile that indicates that the user is a priority user could have an associated threshold that is lower than a regular user. Similarly, when access network 304 is stressed a message can be sent to mobile device 200 setting the threshold to a larger value.

Continuing with the description of operation 604, the presence module 250 can execute and compare a timestamp for the presence information to the current time and calculate a difference. Presence module 250 can then compare the difference to the threshold and determine whether the presence information is stale. As shown by the figure, if the information is stale the presence engine 400 can run, otherwise the presence module 250 can return the cached presence information to the application as shown by operation 614. Similar to that described above, when the presence information is stale the presence engine 400 can execute and generate a quantification. The quantification can be compared to a threshold and a determination (at 608) can be made as to whether access network resources should be used to update the presence information. In an alternative embodiment instead of generating quantification at operation 606 the presence engine 400 can execute the portion of the operational procedure of FIG. 5 that detects available communication channels and determines whether a new reverse traffic channel needs to be opened. The operational procedure could then branch back to operation 606.

Operation 610 shows that the presence module 250 can determine to update the presence information by determining which server to send a request to from, for example, information that registers a networked location for the desired presence information, and sending a request on a reverse traffic channel to base transceiver station of FIG. 3. Updated presence information can be received and sent to the application (at 614). In the instance that the presence engine 400 determines not to update the information, and state information is not in memory, the request can fail (at 616). For example, a message can be displayed to the user indicating that presence information could not be obtained at this time, the presence module 250 can run through the algorithm again after a predetermined amount of time expires, or the presence module 250 can attempt to obtain the presence information via a different communication channel, e.g., Bluetooth®, Wi-Fi®, etc., similar to that described above with respect to FIG. 5. Continuing with the description, if old presence information is available (at 612) it can be sent to the application. In an alternative embodiment a message can be displayed indicating that the information is old. In the same or an alternative embodiment instead of returning stale presence information, the presence module 250 can attempt to obtain the presence information via a different communication channel similar to that described above with respect to FIG. 5.

Turning to FIG. 7, it illustrates an operational procedure for practicing aspects of the present disclosure. FIG. 7 illustrates an embodiment where the presence module 250 has determined to select a communication channel from a group and send the request via that channel. For example, the presence module 250 can be configured to execute some, or all of the operations illustrated in FIG. 7 in response to receiving a request for presence information from an application, or after some, or all of the operations illustrated in FIGS. 5, 6, and/or 8 are executed.

Operation 700 begins the operational procedure when for example, an application requests presence information, e.g., status information for contacts in an address book application. For example, a user could open a push to talk application and the application could request status information, e.g., information which indicates whether a remote user is “busy,” “available,” etc., for the users in the address book. In response to the request, and as illustrated by operation 702, status information for available communication channels can be obtained. For example, the presence engine 400 can access a data structure in memory that identifies the different available communication channels. Once the data structure is accessed a score can be computed for each available communication channel using an algorithm that factors in at least a preference rating.

A channel can be selected and a request for updated presence information can be sent to a server. Continuing with the push-to-talk example, the push-to-talk application could have previously registered with the presence module 250 and could identify the type of information it uses and a networked server that stores the information. In this example, the presence module 250 can send a request (in the format used to make such requests, i.e., a request that conforms to the protocol used by the presence server) to the presence server via the selected channel and store the updated presence information, e.g., status information for push-to-talk contacts (Operation 706). Operation 708 then shows that the updated presence information can be sent to the requesting application.

Turning to FIG. 8, it illustrates an operational procedure for practicing aspects of the present disclosure. FIG. 8 illustrates an embodiment in which the presence module 250 determines whether to update presence information or return cached information. For example, the presence module 250 can be configured to execute some, or all of the operations illustrated in FIG. 8 in response to receiving a request for presence information from an application, or after some, or all of the operations illustrated in FIGS. 5, 6, and/or 7 are executed.

Operation 800 begins the procedure when, for example, the presence module 250 runs the presence engine 400 to update presence information or return cached information. In the illustrated operational flowchart, operation 802 illustrates that the presence engine 400 can execute and generate a quantification. For example, the quantification could be calculated from an algorithm using load information from base transceiver station 326 and timestamp information. In an exemplary embodiment, the quantification could be generated from an algorithm that takes a value that represents an amount of time presence information has been stored in memory and subtracts it from a value that quantifies the load on the base transceiver station. Operation 804 shows that the quantification can be compared to a threshold and operations 808 and 810 show that the presence engine 400 can update presence information, e.g., receive fresh presence information and store it. Operation 812 shows that cached information to the application based on the result of the comparison operation. Continuing with the specific example above, the threshold could be set to zero. If the calculated quantification is negative, e.g., load is great and length of time presence information is cached is short, the presence engine 400 can be configured to return cached information. If the calculated quantification is positive then the presence engine 400 can be configured to send the request.

In the various embodiments described above, the mobile device processor executing the presence module may be configured to accommodate presence information update requests from presence-aware applications associated with a single user (i.e., a dedicated user, such as the registered owner of the mobile device). Thus, when a presence-aware application requests updated presence information, the mobile device processor executing the presence module may make the determination of whether to update presence information based on the characteristics of that dedicated, sole user's profile. For example, the processor executing the presence module may have a higher likelihood of updating presence information when the owner of the device is an emergency-personnel user.

In further embodiments, a mobile device and/or the presence-aware applications running on the device may be configured to support multiple user profiles that have varying characteristics, privileges, attributes, services, etc. For instance, multiple users with access to the same mobile device may each create a user profile and login credentials on that device, and each user may take turns using the mobile device (e.g., one user may log in/access the mobile device after another user has finished/logged out of the device). The mobile device may also allow multiple users to access the device and/or presence-aware applications simultaneously (e.g., a gaming device that supports multiple players). In such embodiments, the mobile device processor executing the presence module and/or presence engine may be configured to associate a particular user profile with a request for updated presence information. The mobile device processor executing the presence module/engine may determine whether to process the request for updated presence information based at least in part on the user profile associated with the request. Thus, the mobile device processor executing the presence module/engine may manage presence information for multiple user profiles present on the mobile device.

FIG. 9 is a system block diagram 900 illustrating a mobile device 901 configured to support multiple user profiles stored on the device 901. In an embodiment, a presence module 250 operating on the mobile device 901 may be configured to manage and update presence information associated with one or more user profiles 902, 904 stored on the mobile device 901 as described below.

The user profiles 902, 904 may each include information and characteristics associated with a user, such as each user's preferences for using the mobile device, customized features and settings, and information identifying relevant presence information (e.g., available contacts, device state information, geographic location information, etc.). The user profiles 902, 904 may also be configurable, and a mobile device processor (e.g., logical processor 102) may be configured to change one or more characteristics, attributes, settings, etc. associated with a user profile in response to receiving a user input from a user interface device directed at that particular user profile. In a further embodiment, an administrative or “super” user on the mobile device may configure the presence information settings or other information for profiles of other users of the device (e.g., “guest” profiles).

In an embodiment, the user profiles 902, 904 may interface with presence-aware applications (e.g., applications 402, 404, 406 as described above with reference to FIG. 4) such that the applications may have access to or otherwise utilize presence information associated with user profiles 902, 904. For example, a user may log into the application 404 associated with one user profile 904, and the application 404 may load a contact list that utilizes presence information included in or associated with the user profile 904.

In an embodiment, multiple instances of an application may execute simultaneously on the mobile device 901, and each instance of the application may be associated with a separate user profile 902, 904. For example, a first instance of the application 406 may be launched using a first user profile 902 (e.g., the credentials for the first user profile 902 were used to log into the first instance of the application 406), and while the first instance is running, a second instance of the application 406 may be launched using a second user profile 904. In another embodiment, multiple user profiles may be simultaneously associated with the same application. For example, two user profiles 902, 904 may be logged into or associated with an application 402 (e.g., a computer game) at the same time.

As discussed above with reference to FIG. 4, the presence module 250 may serve as a single point of contact on the mobile device 901 for presence information requests. In further embodiments, the presence module 250 may process presence information update requests associated with one or more user profiles 902, 904. In an embodiment, user profiles 902, 904 may directly interface with the presence module 250, and the presence module 250 may manage the presence information for the user profiles 902, 904 in a manner similar to how the presence module 250 manages presence information for applications 402, 404, 406 that is described above with reference to FIG. 4. In other words, like presence-aware applications, the user profiles 902, 904 may be configured to utilize presence information and to request presence information updates directly from the presence module 250.

The user profiles 902, 904 may also be configured to interface with the presence module 250 through associations with one or more applications 402, 404, 406. In an embodiment, the user profiles 902, 904 may register with, log in to, or otherwise become associated with one or more of applications 402, 404, 406. In such an embodiment, the applications 402, 404, 406 may be registered with the presence module 250 and may request presence information updates on behalf of the user profiles 902, 904.

As described above, user profiles 902, 904 may include information (e.g., priority of the user, importance of having the latest presence information, desired frequency of presence information updates, etc.) that the presence module 250 and/or the presence engine 400 may utilize when determining whether to update presence information in response to receiving a presence information update request associated with the user profiles 902, 904. Thus, in an embodiment, the presence module 250 may efficiently process presence information update requests by performing a cost calculation to determine whether processing a request for updated presence information would require an excessive amount of resources (e.g., power, processing, network bandwidth, etc.) based at least in part on the characteristics of the user profile associated with the request for updated presence information as further described below with reference to FIG. 10. When the presence module 250 and/or the presence engine 400 determine that presence information should be updated, the presence module 250 may obtain presence information from presence servers 330 using various mechanisms as described above with reference to FIG. 4, including via a communication port 408 or wireless transceiver 410.

FIG. 10 illustrates an embodiment method 1000 that may be implemented by a mobile device processor executing the presence module for determining whether to process a presence information update request associated with a particular user profile. In an embodiment, in response to receiving a presence update request, a mobile device processor may perform a cost calculation based at least in part on the particular user profile associated with the presence update request to determine whether to update the presence information as mentioned above.

In block 1002, the processor executing the presence module may receive a presence update request from a requesting entity, such as an application attempting to refresh current location information for the mobile device or directly from a user profile.

The processor executing the presence module may optionally determine whether the presence module is enabled in optional determination block 1004. In other words, the processor executing the presence module may determine whether performing a cost calculation analysis for updating presence information is not necessary, such as when the device currently has sufficiently battery power (e.g., when it is powered through a wall outlet) and/or when the device's access network has low traffic and/or high bandwidth. Thus, when the processor executing the presence module determines that the presence engine is disabled (i.e., optional determination block 1004=“No”), the processor may update and send the updated presence information to the requesting entity by performing operations 1016-1024 as described below.

When the processor executing the presence module determines that the presence engine is enabled (i.e., optional determination block 1004=“Yes”), the processor may also optionally determine whether there is presence information stored in memory that is up to date in optional determination block 1006 as generally described above with reference to FIG. 6. In an embodiment, the processor executing the presence module may attempt to update presence information only when an update timer has elapsed (i.e., after a certain period of time has elapsed since the last presence information update). In other words, the processor executing the presence module may save time and resources by updating presence information only after the current presence information has become out of date or “stale.” For example, the processor may ignore a request to update location information received within a second of receiving a previous request because the mobile device's location may not have substantially changed within that second. When the processor determines that the current presence information is up to date (i.e., optional determination block 1006=“Yes”), the processor may send stored presence information to the requesting entity in block 1026.

When the processor executing the presence module determines that the current presence information is stale or out of date (i.e., optional determination block 1006=“No”), the processor may continue by determining a user profile associated with the presence update request in block 1008. In an embodiment, the user profile may be directly associated with the request for updated presence information. For example, the user may have logged directly into the application requesting updated presence information using a particular user profile or a log-in process (e.g., entry of a password or user ID) that enabled the application to select and use that user's profile. In another embodiment, the user profile may be indirectly or generally associated with the presence update request. For example, the processor executing the presence module may determine that a user profile associated with the underlying operating system is associated with the presence update request. In another embodiment, a profile associated with the application (e.g., an application-specific user profile) may supersede a more generic/broader profile (e.g., a user profile for the underlying operating system). In another embodiment, multiple user profiles may be logged into or associated with an application simultaneously, and the processor executing the presence module may determine the particular user profile associated with the request for updated presence information, such as by identifying the user profile that is logged into the application requesting updated presence information.

In block 1010, the processor executing the presence module may calculate an update quantification based at least in part on the user profile determined in block 1008. As described above, the processor executing the presence module may perform an algorithm that incorporates values related to various aspects (e.g., channel performance information, available communication channels, values assigned by access technologies, etc.) to produce a quantification value that may be used in determining whether to update the presence information as further described below. In an embodiment, the mobile device processor executing the presence module may also factor into this algorithm the user profile determined in block 1008 such that certain characteristics of the user profile may affect the likelihood that the processor executing the presence module will update the presence information. For example, a user profile associated with the owner of the mobile device (e.g., a super user or “owner” profile) may generate a higher quantification value or score than another user profile associated with a “guest” profile. In a further example, the processor executing the presence module may process a presence update request associated with an “owner” profile in most or all circumstances but may not update presence information for a “guest” profile unless the mobile device detects an available Wi-Fi network.

In an embodiment described above, user profile characteristics may be configurable via user inputs received through a user interface device (e.g., a keyboard, touchscreen, mouse, etc.), thereby enabling users or the owner of the mobile device to customize the conditions in which the processor executing the presence module may honor a presence information update request. For example, in response to the processor receiving user inputs from the owner of the device, the processor may configure a “guest” user profile such that processor executing the presence module may not honor presence information update requests from the “guest” profile unless the mobile device has access to a Wi-Fi network and the device's battery is charged above 75%. In a further embodiment, the processor executing the presence module may calculate the quantification based on values or settings included in the user profile as described above with reference to FIG. 9.

In block 1012, the processor executing the presence module may determine a threshold value for updating presence information. As described above in various embodiments, the threshold value may correspond to current conditions on the mobile device, network conditions, etc. The processor executing the presence module may also compare the update quantification with the threshold value in block 1014.

In determination block 1016, the processor executing the presence module may also determine whether the presence information requires updating based at least in part on the comparison made in block 1014. When the processor executing the presence module determines that the presence information does not require updating based on the comparison (i.e., determination block 1016=“No”), the processor may return stored presence information to the requesting entity in block 1026 as described above.

When the processor executing the presence module determines that the presence information does require updating based on the comparison (i.e., determination block 1016=“Yes”), the processor may select an available communication channel in block 1018, such as by obtaining state information for available communication channels and selecting the best available communication channel as generally described above with reference to block 702, 704 described of FIG. 7. The processor executing the presence module may also update the presence information via the selected communication channel in block 1020 by communicating with a presence server as described above with reference to FIG. 3.

In block 1022, the processor executing the presence module may store the updated presence information in memory as described above with reference to blocks 514, 610, 706, 810 of FIGS. 5-8. The mobile device processor executing the presence module may also send the updated presence information to the requesting entity in block 1024.

The various embodiment methods may be implemented in a processor of a mobile device by configuring the processor with processor-executable computer program code. Such “program code” for execution on a programmable processor for carrying out operations of the various embodiment methods may be written in a high level programming language such as C, C++, C#, Smalltalk, Java, JavaScript, Visual Basic, a Structured Query Language (e.g., Transact-SQL), Perl, or in various other programming languages. Program code or programs stored on a non-transitory processor-readable or computer-readable storage medium as used in this application may refer to machine language code (such as object code) whose format is understandable by a processor.

Many computing devices operating system kernels are organized into a user space (where non-privileged code runs) and a kernel space (where privileged code runs). This separation is of particular importance in Android® and other general public license (GPL) environments where code that is part of the kernel space must be GPL licensed, while code running in the user-space may not be GPL licensed. It should be understood that the various software components/units discussed herein may be implemented in either the kernel space or the user space, unless expressly stated otherwise.

The foregoing method descriptions and the process flow diagrams are provided merely as illustrative examples and are not intended to require or imply that the steps of the various embodiments must be performed in the order presented. As will be appreciated by one of skill in the art the order of steps in the foregoing aspects may be performed in any order. Words such as “thereafter,” “then,” “next,” etc. are not intended to limit the order of the steps; these words are simply used to guide the reader through the description of the methods. Further, any reference to claim elements in the singular, for example, using the articles “a,” “an” or “the” is not to be construed as limiting the element to the singular.

As used in this application, the terms “component,” “module,” “system,” “engine,” “generator,” “unit,” “manager” and the like are intended to include a computer-related entity, such as, but not limited to, hardware, firmware, a combination of hardware and software, software, or software in execution, which are configured to perform particular operations or functions. For example, a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device may be referred to as a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one processor or core and/or distributed between two or more processors or cores. In addition, these components may execute from various non-transitory computer readable media having stored thereon various processor-executable instructions and/or data structures. Components may communicate by way of local and/or remote processes, function or procedure calls, electronic signals, data packets, memory read/writes, and other known network, computer, processor, and/or process related communication methodologies.

The various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

The hardware used to implement the various illustrative logics, logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a multiprocessor, but, in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a multiprocessor, a plurality of multiprocessors, one or more multiprocessors in conjunction with a DSP core, or any other such configuration. Alternatively, some steps or methods may be performed by circuitry that is specific to a given function.

In one or more exemplary aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or code on a non-transitory computer-readable medium or non-transitory processor-readable medium. The steps of a method or algorithm disclosed herein may be embodied in a processor-executable software module that may reside on a non-transitory computer-readable or processor-readable storage medium. Non-transitory computer-readable or processor-readable storage media may be any storage media that may be accessed by a computer or a processor. By way of example but not limitation, such non-transitory computer-readable or processor-readable media may include RAM, ROM, EEPROM, FLASH memory, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to store desired program code in the form of instructions or data structures and that may be accessed by a computer. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of non-transitory computer-readable and processor-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and/or instructions on a non-transitory processor-readable medium and/or computer-readable medium, which may be incorporated into a computer program product.

The foregoing detailed description has set forth various embodiments of the systems and/or processes via examples and/or operational diagrams. Insofar as such block diagrams, and/or examples contain one or more functions and/or operations, it will be understood by those within the art that each function and/or operation within such block diagrams, or examples can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof.

While particular aspects of the present subject matter described herein have been shown and described, it will be apparent to those skilled in the art that, based upon the teachings herein, changes and modifications may be made without departing from the subject matter described herein and its broader aspects and, therefore, the appended claims are to encompass within their scope all such changes and modifications as are within the true spirit and scope of the subject matter described herein. 

What is claimed is:
 1. A method of updating presence information on a mobile device configured to support multiple user profiles, comprising: receiving in a processor of the mobile device a request to update presence information from a requesting entity executing on the mobile device; determining in the processor a user profile associated with the request from among the multiple user profiles; calculating in the processor an update quantification based at least in part on the determined user profile; comparing in the processor the update quantification to a threshold value; determining in the processor whether the presence information requires updating based at least in part on the comparison; selecting one of a plurality of available communication channels in response to the processor determining that the presence information requires updating, wherein each communication channel of the plurality of available communication channels is associated with a different communication protocol; and updating the presence information via the selected communication channel.
 2. The method of claim 1, further comprising determining in the processor whether any of the plurality of available communication channels is already open, wherein selecting one of a plurality of available communication channels comprises selecting an already open channel in the plurality of available communication channels when any channel of the plurality of available communication channels is already open.
 3. The method of claim 1, wherein the presence information includes at least one of a capability of a second mobile device, a state of the second mobile device, a geographic location of the second mobile device, and user configurable status information associated with the second mobile device.
 4. The method of claim 1, further comprising: determining in the processor whether presence information stored in memory is up to date in response to receiving the request; and sending the stored presence information to the requesting entity in response to the processor determining that the presence information stored in memory is up to date.
 5. The method of claim 1, further comprising: storing the updated presence information in a memory of the mobile device; and sending the updated presence information to the requesting entity.
 6. The method of claim 1, wherein the multiple user profiles are simultaneously active on the mobile device.
 7. A mobile device, comprising: a memory; and a processor configured with processor-executable instructions to perform operations comprising: receiving a request to update presence information from a requesting entity executing on the mobile device; determining a user profile associated with the request from among multiple user profiles; calculating an update quantification based at least in part on the determined user profile; comparing the update quantification to a threshold value; determining whether the presence information requires updating based at least in part on the comparison; selecting one of a plurality of available communication channels in response to determining that the presence information requires updating, wherein each communication channel of the plurality of available communication channels is associated with a different communication protocol; and updating the presence information via the selected communication channel.
 8. The mobile device of claim 7, wherein: the processor is configured with processor-executable instructions to perform operations further comprising determining whether any of the plurality of available communication channels is already open; and the processor is configured with processor-executable instructions to perform operations such that selecting one of a plurality of available communication channels comprises selecting an already open channel in the plurality of available communication channels when any channel of the plurality of available communication channels is already open.
 9. The mobile device of claim 7, wherein the processor is configured with processor-executable instructions to perform operations such that the presence information includes at least one of a capability of a second mobile device, a state of the second mobile device, a geographic location of the second mobile device, and user configurable status information associated with the second mobile device.
 10. The mobile device of claim 7, wherein the processor is configured with processor-executable instructions to perform operations further comprising: determining whether presence information stored in memory is up to date in response to receiving the request; and sending the stored presence information to the requesting entity in response to determining that the presence information stored in memory is up to date.
 11. The mobile device of claim 7, wherein the processor is configured with processor-executable instructions to perform operations further comprising: storing the updated presence information in the memory; and sending the updated presence information to the requesting entity.
 12. The mobile device of claim 7, wherein the processor is configured with processor-executable instructions to perform operations such that the multiple user profiles are simultaneously active on the mobile device.
 13. A mobile device, comprising: means for receiving a request to update presence information from a requesting entity executing on the mobile device; means for determining a user profile associated with the request from among multiple user profiles; means for calculating an update quantification based at least in part on the determined user profile; means for comparing the update quantification to a threshold value; means for determining whether the presence information requires updating based at least in part on the comparison; means for selecting one of a plurality of available communication channels in response to determining that the presence information requires updating, wherein each communication channel of the plurality of available communication channels is associated with a different communication protocol; and means for updating the presence information via the selected communication channel.
 14. The mobile device of claim 13, further comprising means for determining whether any of the plurality of available communication channels is already open, wherein means for selecting one of a plurality of available communication channels comprises means for selecting an already open channel in the plurality of available communication channels when any channel of the plurality of available communication channels is already open.
 15. The mobile device of claim 13, wherein the presence information includes at least one of a capability of a second mobile device, a state of the second mobile device, a geographic location of the second mobile device, and user configurable status information associated with the second mobile device.
 16. The mobile device of claim 13, further comprising: means for determining whether presence information stored in memory is up to date in response to receiving the request; and means for sending the stored presence information to the requesting entity in response to determining that the presence information stored in memory is up to date.
 17. The mobile device of claim 13, further comprising: means for storing the updated presence information in a memory of the mobile device; and means for sending the updated presence information to the requesting entity.
 18. The mobile device of claim 13, wherein the multiple user profiles are simultaneously active on the mobile device.
 19. A non-transitory processor-readable storage medium having stored thereon processor-executable instructions, wherein the stored processor-executable instructions are configured to cause a processor of a mobile device to perform operations comprising: receiving a request to update presence information from a requesting entity executing on the mobile device; determining a user profile associated with the request from among multiple user profiles; calculating an update quantification based at least in part on the determined user profile; comparing the update quantification to a threshold value; determining whether the presence information requires updating based at least in part on the comparison; selecting one of a plurality of available communication channels in response to determining that the presence information requires updating, wherein each communication channel of the plurality of available communication channels is associated with a different communication protocol; and updating the presence information via the selected communication channel.
 20. The non-transitory processor-readable storage medium of claim 19, wherein: the stored processor-executable instructions are configured to cause a mobile device processor to perform operations further comprising determining whether any of the plurality of available communication channels is already open; and the stored processor-executable instructions are configured to cause a mobile device processor to perform operations such that selecting one of a plurality of available communication channels comprises selecting an already open channel in the plurality of available communication channels when any channel of the plurality of available communication channels is already open.
 21. The non-transitory processor-readable storage medium of claim 19, wherein the stored processor-executable instructions are configured to cause a mobile device processor to perform operations such that the presence information includes at least one of a capability of a second mobile device, a state of the second mobile device, a geographic location of the second mobile device, and user configurable status information associated with the second mobile device.
 22. The non-transitory processor-readable storage medium of claim 19, wherein the stored processor-executable instructions are configured to cause a mobile device processor to perform operations further comprising: determining whether presence information stored in memory is up to date in response to receiving the request; and sending the stored presence information to the requesting entity in response to determining that the presence information stored in memory is up to date.
 23. The non-transitory processor-readable storage medium of claim 19, wherein the stored processor-executable instructions are configured to cause a mobile device processor to perform operations further comprising: storing the updated presence information in a memory of the mobile device; and sending the updated presence information to the requesting entity.
 24. The non-transitory processor-readable storage medium of claim 19, wherein the stored processor-executable instructions are configured to cause a mobile device processor to perform operations such that the multiple user profiles are simultaneously active on the mobile device. 